Proactive browser content analysis

ABSTRACT

A protection module operates to analyze threats, at the protocol level (e.g., at the HTML level), by intercepting all requests that a browser engine resident in a computing device sends and receives, and the protection agent completes the requests without the help of the browser engine. And then the protection module analyzes and/or modifies the completed data before the browser engine has access to it, to, for example, display it. After performing all of its processing, removing, and/or adding any code as needed, the protection module provides the HTML content to the browser engine, and the browser engine receives responses from the protection agent as if it was speaking to an actual web server, when in fact, browser engine is speaking to an analysis engine of the protection module.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefits of and priority, under 35U.S.C. §119(e), to U.S. Provisional Application No. 61/542,693, filedOct. 3, 2011, entitled “PROACTIVE BROWSER CONTENT ANALYSIS,” which isincorporated herein by this reference in its entirety for all that isteaches and for all purposes.

FIELD

An exemplary aspect of the present invention generally relates tocomputer system management. In particular, but not by way of limitation,an exemplary aspect relates to systems and methods for controllingpestware or malware or other undesirable or unwanted applications and/orinstructions.

BACKGROUND

Personal computers and business computers are continually attacked byviruses, trojans, spyware, adware, etc, collectively referred to as“malware” or “pestware.” These types of programs generally act to gatherinformation about a person or organization—often without the person ororganization's knowledge. Some pestware is highly malicious. Otherpestware is non-malicious but may cause issues with privacy or systemperformance. And yet other pestware is actually beneficial or wanted bythe user. Wanted pestware is sometimes not characterized as “pestware”or “spyware.” But, unless specified otherwise, “pestware” or “malware”as used herein refers to any program that is malicious in some wayand/or collects and/or reports information about a person or anorganization and any “watcher processes” related to the pestware ormalware.

SUMMARY

In accordance with an exemplary aspect, a protection module operates toanalyze threats, at the protocol level (e.g., at the HTML level), byintercepting all requests that a browser engine resident in a computingdevice sends and receives, and the protection agent completes therequests without the help of the browser engine.

And then the protection module analyzes and/or modifies the completeddata before the browser engine has access to it, to, for example,display it. After performing all of its processing, removing, and/oradding any code as needed, the protection module provides the HTMLcontent to the browser engine, and the browser engine receives responsesfrom the protection agent as if it was speaking to an actual web server,when in fact, browser engine is speaking to an analysis engine of theprotection module.

This allows the protection module to have control over what a browserengine “sees,” providing means to remove any exploits, malware, andother threats dynamically. This also enables the protection module toadd content into the browser stream at the HTML level, before receipt bythe browser.

In some exemplary implementations, search engine results (e.g., resultsprovided by Google®, Yahoo®, and Bing®) are annotated/updated/amended bythe protection module—within the HTML code—to denote if a particularwebsite is legitimate or malicious. For example, a legitimate link inthe search results may be depicted in connection with a green check markand a suspect link may be depicted with a red cross. (Of course otherindicators could also be used that identify to a user whether or not alink is “good,” “bad,” or “unknown.) In addition to search resultannotation, the protocol-level analysis approach may also be used inconnection with anti-phishing and URL analysis among other types ofanalysis.

The differences between the disclosed protocol-level analysis approachcompared to other prior anti-malware approaches are significant. In thecontext of search result annotation for example, the data (e.g., a webpage of search results) is first analyzed and modified by an analysisengine of the protection module, which has control over every element ofa web page before the web page is operated on by the browser engine.This is in contrast to prior approaches that just make high-levelmodifications to the content after the content has been rendered anddisplayed through a Browser Helper Object. With an exemplary aspect ofthe present protocol-level approach, there is virtually no performanceoverhead, and in many cases, there is actually a performance improvementwhen performing the browser content analysis.

When the protection module receives content from a web server, theprotection module then, if necessary, decrypts and decompresses the webcontent and then assembles the requested web page (e.g., in a decryptedand decompressed HTML format that the web page existed in at the remoteserver). The protection module then analyzes the web page to determinewhether the web page includes links that may lead to sites hostingmalware or whether the web page itself includes malware. The analysis ofthe assembled web page may include communicating with a remote securitycenter so that a malware management analysis may be performed to analyzeone or more portions of the content of the assembled web page and/or theprotection module itself may perform analysis of content of theassembled webpage. The analyzed webpage can then be forwarded to the webbrowser for display to a user.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates an exemplary embodiment of a computing environmentaccording to an exemplary embodiment.

FIG. 2 illustrates an exemplary embodiment of systems and operations atthe remote computer.

FIG. 3 is a flowchart illustrating exemplary process flow at the remotecomputer.

FIG. 4 illustrates an exemplary embodiment of one of the computers inFIG. 1.

DETAILED DESCRIPTION

Referring now to the drawings, where like or similar elements aredesignated with identical reference numerals throughout the severalviews, and referring in particular to FIG. 1, it is a block diagramdepicting an environment in which several embodiments of the inventionmay be implemented. As shown, a security center 102 (also referred toherein as a “central” or “base” computer), remote user 104 operating aremote computer 105, a malware source 106, and a web server 108 are allcommunicatively coupled through one or more networks (e.g., the Internetand/or local or wide area networks) 110 and links 5. Although only oneremote user 104, remote computer 105, malware source 106, web server108, and security center 102 are depicted, each of these logicallyrepresents a potentially unlimited number of persons, entities and/orcomputers or computing resources.

The remote user 104 may be a an individual or a business enterprise thatoperates the remote computer 105, which may each be a personal computer,a server of any type, a PDA, mobile phone, tablet, netbook, aninteractive television, or any other device capable of loading andoperating computer objects.

In the depicted environment, the malware source 106 generally representsa source of malware that ends up or is strategically placed at the webserver 108, which may or may not be suspected of hosting malware. Forexample, the malware source 106 may generate a malware object in avariety of forms including in a scripting language such asECMAscript-based scripting languages (e.g., JavaScript or Adobe Flash),but the malware source may generate other types of objects such ascomputer files, part of a file or a sub-program, an instruction(s),macro, web page or any other piece of code to be operated by or on thecomputer, or any other event whether executed, emulated, simulated orinterpreted.

As depicted, the security center 102 is disposed and configured to beaccessible to the user 104 so that, as discussed further herein, thesecurity center 102 may facilitate the management of malware on theremote computer 104. In many implementations, the security center 102operates according to a Software as a Service (SaaS) business model togenerally provide Web security services “in the cloud.”

As depicted in FIG. 1, the exemplary security center 102 includes amalware management portion 112 that is coupled to a data store 114.Although not depicted, the security center 102 may also includecomponents that provide other services (e.g., internet policyenforcement, in/outbound content control, application control,compliance-related services, etc.).

The security center 102 is generally configured to obtain informationabout malware threats and to be a resource for the remote computer 105to enable the remote computer to manage malware threats more effectivelyand efficiently. It should be noted that that the malware managementcomponent 112 and data store 114 are presented for convenience as singleentities, but the security center 102 can be scaled and comprised ofmultiple geographically distributed computers and servers, etc., and thedata store can be made up multiple databases and storage distributedaround this central system and/or be located in a cloud-typeenvironment.

Although not required, the malware management 112 component of thesecurity center 102 may maintain the data store 114 as a communitydatabase that is populated, over time, with information relating to eachobject run on all of the connected remote computers as disclosed in US A2007/0016953, published 18 Jan. 2007, entitled “METHODS AND APPARATUSFOR DEALING WITH MALWARE,” the entire contents of which are herebyincorporated herein by reference. As discussed in the above-identifiedapplication, data representative of each malware object may take theform of a so-called signature or key relating to and/or identifying theobject, its attributes and/or behavior(s).

In operation, the protection agent 116 in this embodiment operates toanalyze threats, at the protocol level (e.g., at the HTML level), byintercepting all requests that the browser engine 118 sends andreceives, and the protection agent 116 completes the requests withoutthe help of the browser engine 118. And then the protection agent 116analyzes and/or modifies the completed data before the browser engine118 has access to it. After performing all of its processing, removing,and/or adding any code as needed, the protection agent feeds the HTMLcontent back to the browser engine 118, and the browser engine 118receives responses from the protection agent 116 as if it was “speaking”to an actual web server (e.g., web server 108) when in fact, it isspeaking to an analysis engine of the protection agent 116. This allowsthe protection agent 116 to have full control over what the browserengine 118 “sees,” providing means to remove any exploits, malware, andother threats dynamically. This also enables the protection agent 116 toadd content into the browser stream at the HTML level. Stated anotherway, the protection agent 116 caches web content requested by a browser,analyzes and/or modifies the retrieved web content, and provides a cleanor sanitized version of the web content, free of malware, to thebrowser.

In some optional implementations for example, search engine results(e.g., results provided by Google, Yahoo, and Bing) are annotated by theprotection agent 116—within the HTML code—to denote if a particularwebsite is legitimate or malicious. For example, a legitimate link inthe search results may be depicted in connection with a green check markand a suspect link may be depicted with a red cross. In addition tosearch result annotation, the protocol-level analysis approach may alsobe used in connection with anti-phishing and URL analysis among othertypes of analysis.

The differences between the protocol-level analysis approach disclosedherein as compared to other prior anti-malware approaches aresignificant. In the context of search result annotation for example, thedata (e.g., a web page of search results) is first analyzed and modifiedby an analysis engine of the protection agent 116, which has fullcontrol over every element of the web page before the page is operatedon by the browser engine 118. This is in contrast to prior approachesthat just make high-level modifications to the content after it has beendisplayed through a Browser Helper Object. With the presentprotocol-level approach, there is virtually no performance overhead, andin many cases, there is actually a performance improvement whenperforming the browser content analysis.

When the protection agent 116 receives content from the web server 108,the protection agent 116 then, if necessary, decrypts and decompressesthe web content and then assembles the requested web page (e.g., in adecrypted and decompressed HTML format that the web page existed in atthe remote server 108). The protection agent 116 then analyzes the webpage to determine whether the web page includes links that may lead tosites hosting malware or whether the web page itself includes malware.The analysis of the assembled web page may include communicating withthe security center 102 so that the malware management component 112 mayanalyze one or more portions of the content of the assembled web pageand/or the protection agent 116 itself may perform analysis of contentof the assembled webpage.

In many embodiments, the cleaning process that the protection agent 116carries out takes place through a highly optimized routine written in,for example, raw C with an inline assembler reducing processing effortwithin the browser engine 118 itself bydecrypting/decompressing/de-encoding any of the content outside of thebrowser engine 118. Having full control at this level also means thatcomplex inferential algorithms can be applied to the browser content asa whole, taking into account any external script/image links, to buildan in-memory picture of the final content before it is rendered to theuser by the browser on a display (not shown). This general operation canbe extended to remove/modify any form of content, whether illicitimages, ads, fake password request forms, malicious exploits, cross sitescripting attacks (XSS), etc.

Referring to FIG. 2, shown is a block diagram depicting exemplaryfunctional components and operations that reside and take place on theremote computer 105 at the location of the remote user 104. In thedepiction of FIG. 2, the browser-related processes andprotection-agent-related processes are separated so that the interactionbetween the two types of processes may be more clearly understood. Whilereferring to FIG. 2, simultaneous reference is also made to FIG. 3,which depicts exemplary aspects of the process flow that occurs inconnection with the components depicted in FIG. 2. Depicted next to eachof the blocks in FIG. 3 is either a “K” or a “U,” which indicate thatthe operation is implemented at the kernel or user-level, respectively.It should be recognized, however, that the operations described withreference to FIGS. 2 and 3 may be implemented with some kernel-modeoperations being implemented at the user-level and vice versa. Moreover,the illustrated arrangement of components in FIGS. 2 and 3 is logical,and is not meant to be an actual hardware diagram. Thus, many of thecomponents can be combined and/or further separated in an actualimplementation.

As shown, the browser processes in this embodiment include agentprocesses 220 that are installed on the remote computer 105 inconnection with the protection agent 116 so that functions of theprotection agent 116 are integrated with a typical browser engine 218.In other words, the agent processes 220 of the browser processes areimplemented by additional of code that is wrapped around a typicalbrowser engine 218 to intercept what is requested and received. Asdiscussed further herein, these agent processes 220 enable all contentthat is requested by an application 222 (e.g., a browser) and receivedby the browser engine 218 to be intercepted.

More specifically as shown, when a user initiates a request via theapplication 222 (e.g., web browser or other application that requestsweb content), a connection request 360 is initiated as a POST/GETrequest 362 to a website (e.g., hosted by the webserver 108) and theanalysis engine 224 looks at the context of the request to assesswhether the request is the first request in a session (Block 364), andif the request is the first request, a determination is made as towhether the request is associated with known, malicious content (Block366), and if so, the request is blocked (Blocks 368, 370).

In some embodiments, the analysis engine 224 accesses the securitycenter 102 via the Internet and the security center 102 is utilized tofacilitate whether the request is a request for known malicious content(e.g., the URL of the request may be compared to a black list of URLs).But the analysis engine 224 may also include some malware checkingfunctionality locally. As shown, if the request is not blocked, therequest may be pre-processed by the content acquisition component 226(Block 372) (e.g., to set aside sufficient memory in RAM in anticipationof the content from the website being received) before the request issent to the destination website 108.

And as shown, when the first response is received by the contentacquisition component 226 (Block 374), if the response is not complete,the response is stored in memory (Block 376), and the next request issent to the destination website 108 (Block 378). In this way, thecontent acquisition component 226 continues to obtain content from thewebsite 108 (Blocks 374, 376, 378) until the web page is complete, andthe complete page is held in memory by the content acquisition component226.

Thus, in short, the initial request 360 by the application (e.g.,browser) is intercepted and if the request does not appear to be arequest for malicious content, the content acquisition component 226iteratively sends requests and receives content (Blocks 374, 376, 378)from the website 108 until the requested content has been completelyreceived. This is very different from the ordinary operation of thebrowser engine 218, which would (if unaltered by the protection agent116) obtain the content from the webserver 108 itself by way of a seriesof GET requests.

As shown in FIG. 2, once the web content is completely gathered by thecontent acquisition component 226, the content is passed along to theservice process component 228 via the user process component 230, andthe data is then preprocessed (Block 380), if necessary, to decrypt,remove chunks, and decompress the gathered content. When a web page isreceived from the webserver 108, it may be compressed, chunked encoded,and encrypted, and decompressing, decoding and unencrypting the contentenables a complete picture of the webpage looked like before if any ofthe these forms of obfuscation were applied to the content by thewebserver 108. One of ordinary skill in the art will appreciate thatvarious layers of encoding and compression may be applied to content,but for simplicity, these known details are not included herein forclarity.

And after the data is decrypted and decompressed, the data is in an HTMLformat, so at this point, the protection has the content in the sameHTML format that the website 108 had the content in. And at this pointthe browser engine 218 is unaware that the requested content (e.g., anentire webpage) has been received. As a consequence, the browser pagemay be analyzed by the protocol-level analysis/modification component382 depicted in FIG. 3 outside of the context of the browser engine 218before the browser engine 218 has operated on the webpage. For example,all the links in the webpage, all the pictures in the webpage, and anyscripts in the webpage may be analyzed at a low level of granularity.And code may be changed, enhanced, and removed according to defaultmodes and/or user-configurable mode of operation. As one particularexample, if a malicious script is found, it may be commented out beforethe content is handed to the browser engine.

In addition, in many modes of operation the protocol-levelanalysis/modification component 382 modifies and/or annotates thecontent—as HTML within the content—to provide the user with textual,audible and/or graphical indicators of risk associated with the content.In the context of a webpage that include search results from a user'ssearch query, for example, a green check may be added within the HTMLcode next to a result that is a low risk link, and a red X may be addedwithin the HTML code next to a result the is a high risk link. Forexample, an image tag and/or text may be added within the HTML toindicate a risk of being exposed to malware. Beneficially, makingmodifications to the content (e.g., to include risk indicators) at theHTML level avoids having to address the differences that differentbrowsers introduce into the presentation of rendered content.

This approach of modifying content at the HTML level (e.g., to addannotations) is very different than the prior approaches of rendering(e.g., using a Browser Helper Object) annotations on top of a page thathas already be parsed and rendered by a browser engine. This priorapproach is problematic because it allows the browser engine topotentially execute malicious scripts or perform malicious actions whileit is parsing and rendering the code. And in addition, because theannotations are added after rending, the annotation process must accountfor the rendering differences (e.g., differences in how and wherecontent is displayed) that different browsers (e.g., Firefox, Safari,Chrome, Internet Explorer, etc.) exhibit.

It should be recognized that although search results annotation is oneapplication for the protocol-level (e.g., HTML level) handling ofcontent, it is certainly contemplated that there are otheranti-malware-related applications of the protocol-level handling ofcontent. One application for example, is an anti-phishing application,which may automatically modify HTML data so that user need not type in apassword and expose the password to a keylogger object.

As shown in FIG. 2, more details of the protocol-levelanalysis/modification component 382 are depicted. As shown, once acomplete collection of content is received, the service process 228 isutilized to initiate parsing of the HTML content and extraction of anyscripts 230 in the content before building a tree representation of thecontent 234, which is then asynchronously analyzed 236. As shown in FIG.2 for example, the analysis may include URL analysis 238, IP analysis240, image analysis (e.g., to analyze phishing threat) 242, andscript/HTML analysis 244. The results of the analysis are thenaggregated by the result aggregator 246 so that cloud verification 248may be performed on the single aggregated collection of data by the basecomputer 112 of the security center 102 to determine malwarevulnerabilities.

But in optional embodiments, the verification may be effectuated locallyor in combination with the security center 102. As shown, the results ofthe cloud verification are provided to the final content packager 250 ofthe service process 228, and then in some modes of operation,annotations are performed 252 on the packaged HTML code before beingdistributed 254 back to the data wrapper component 256, which sits ontop of the response receive component of the browser engine 218 andperforms final context modifications 258 to ensure content is properlydisplayed before being passed to the browser engine 218. As shown, finalcontent modifications are performed at 258 before the final content 260is provided to the browser engine 218 for parsing and rendering of theHTML content before being displayed by the application 222.

Referring again to FIG. 3, shown is a loop (Blocks 384, 386, 364) thatdepicts the cleaned and/or annotated content being fed back to thebrowser engine 218. As shown, as the browser engine requests morecontent, the pointer is set to the next byte to be read (Block 384), andonce all the content is on hand, the browser engine requests content(Block 386), and the cleaned and/or annotated content is fed to thebrowser engine 218 in the manner the browser engine 218 would haverequested and received the content.

In other words, from the browser engine's 218 perspective, the browserengine 218 is obtaining the content from the webserver 108 directly. Inother words, the protection agent 116 operates as an emulated server inmemory to provide the clean content in the way the web server 108 wouldhave provided the content to the browser engine 118, 218 if the browserreceived the content form the web server 108 directly.

In the exemplary embodiment however, for operational speed, theclean/modified content is not encoded or encrypted once it is cleaned.As a consequence, the packet headers (e.g., length headers) are modifiedto reflect that the content being provided to the browser engine 118,218 is in a decrypted, decompressed, and/or de-chunked format. In thisway, the browser is not expecting to receive encrypted, encoded,compressed content. Beneficially, the decryption and decompression iscarried out with code implemented in raw C (and most browsers arewritten in a high level language), so the decryption and decompressionare actually carried out faster than an ordinary browser would do so.Additionally, the decryption and decoding is generally carried out afterthe request is complete, so the decryption and decompression is moreefficient than handling the decryption and decompression over severalpasses.

Referring next to FIG. 4, shown is a block diagram depicting hardwarecomponents in an exemplary embodiment of the protected computerdescribed with reference to FIG. 1. As shown, the N processingcomponents 140 described with reference to FIG. 1 are depicted as Nprocessors 440 that are coupled to a bus 460, and also coupled to thebus 460 are a memory 438 (corresponding to memory 138), storage medium412 (corresponding to the storage medium 112), a keyboard/pointingdevice 462, a display/graphics adapter 464, and a network interface 466.In addition, a display 468 is coupled to the display/graphics adapter464.

The storage medium 412 may be any device capable of holding substantialamounts of data, such as a hard drive, flash memory, or some other formof fixed or removable storage device. And the storage medium 412 in thisembodiment stores processor-readable code with instructions toeffectuate the functions described herein (e.g., the functions of thecomponents in FIG. 1 depicted in the user 102 and kernel 104environments). The processors 440 generally function to execute code andprocess other information that resides in memory and may be any specificor general-purpose processor such as an INTEL x86 or POWERPC-compatiblecentral processing unit (CPU), and each may include one or multiple(e.g., four) cores. The memory 438 may include several gigabytes ofrandom access memory, but this is merely exemplary and other memorytypes and sizes may be utilized. As one of ordinarily skill willappreciate, an operating system (e.g., LINUX® or WINDOWS®) may alsoreside in the storage medium 412 and memory 438 and function (e.g., whenexecuted by one or more of the processors 440) to enable the componentsto operate as described with reference to FIG. 1.

As one of ordinary skill in the art in light of this disclosure willappreciate, FIG. 4 depicts only an exemplary embodiment, and theprocesses presented herein are not inherently related to any particularcomputing device or other apparatus. Various general purpose systems maybe used with programs in accordance with the teachings herein, or it mayprove convenient to construct a more specialized apparatus to performthe desired method. In addition, embodiments of the present inventionare not described with reference to any particular programming language.It will be appreciated that a variety of programming languages may beused to implement the teachings of the invention as described herein. Inaddition, it should be understood that operations, capabilities, andfeatures described herein may be implemented with any combinationembodied in firmware, software, application-specific integrated circuits(ASICs), and/or programmable logic devices.

It is to be appreciated that a lesser or more equipped computer systemthan the example described above may be desirable for certainimplementations. Therefore, the configuration of the system illustratedin the figure can vary from implementation to implementation dependingupon numerous factors, such as its intended use, price constraints,performance requirements, storage requirements, technologicalimprovements, and/or other circumstances, or the like.

It should also be noted that while the embodiments and methods describedherein may be performed and used with a computer similar to the onedescribed herein, other embodiments and variations can be used withcomputer that vary from the described example. Therefore, nothingdisclosed herein concerning the configuration of the illustratedcomputer should be construed as limiting the disclosure to a particularembodiment wherein the recited operations are performed by a specificcombination of hardware components.

The various embodiments and variations thereof illustrated in theaccompanying Figures and/or in the totality of this document are merelyexemplary and are not meant to limit the scope of the invention. It isto be appreciated that numerous variations of the invention have beencontemplated as would be obvious to one of ordinary skill in the artwith the benefit of this disclosure. Additionally, while certainfeatures may be categorized under one or more headings to assist withreadability, it is to be appreciated that the feature(s) described undera particular heading may be used in associating with other portions ofthe specification and/or feature(s) described herein. Similarly, whilecertain embodiments are discussed in relation to specific languages, itis to be appreciated that the techniques disclosed herein can be usedwith any software language(s).

While the above described methodology has been discussed in relation toa particular sequence of events, it should be appreciated that minorchanges to this sequence can occur without materially effecting theoperation of the invention.

The above-described system and methodology, as has been indicatedherein, can be implemented on a computing device, such as a personalcomputer, server, dedicated computing device, distributed processingsystem, in a cloud, or the like, or a separately programmed generalpurpose computer. Additionally, the systems and methods of thisinvention can be implemented on a special purpose computer, a programmedmicroprocessor or microcontroller and peripheral integrated circuitelement(s), an ASIC or other integrated circuit, a digital signalprocessor, a hard-wired electronic or logic circuit such as a discreteelement circuit, a programmable logic device such as a PLD, PLA, FPGA,PAL, or the like, in fuzzy logic, artificial intelligence and/or neuralnetworks. In general, any device(s) or module, which can be anycombination of hardware and/or software, capable of implementing a statemachine that is in turn capable of implementing the processes describedherein can be used to implement this invention.

Furthermore, the disclosed methods may readily implemented in softwareusing, for example, object or object-oriented software developmentenvironments that provide portable source code that can be used on avariety of computer or workstation and/or server platforms. The softwarecan be stored on a non-transitory computer-readable medium, with thesoftware including one or more processor executable instructions. Thedisclosed system and methodology may also be implemented partially orfully in hardware using standard logic circuits or, for example, a VLSIdesign. Whether software or hardware is used to implement the systems inaccordance with this invention is dependent on the speed and/orefficiency requirements of the system, the particular function, and theparticular software or hardware systems or microprocessor ormicrocomputer systems being utilized. The systems and methodsillustrated herein can be readily implemented in hardware and/orsoftware using any suitable systems, means, structures, devices and/orthe functionality stored on an appropriate information storage medium,by those of ordinary skill in the applicable art from the functionaldescription provided herein and with a basic general knowledge of thecomputer and software arts.

While the embodiments illustrated herein may show some of the variouscomponents collocated, it is to be appreciated that the variouscomponents of the system can be located at distant portions of adistributed network, such as a communications network and/or theInternet and/or within a dedicated network. Thus, it should beappreciated that the various components can be combined into one or moredevices or collocated on a particular node of a distributed networkand/or in a cloud. As will be appreciated from the description, and forreasons of computational efficiency, the components can be arranged atany location within a distributed network without affecting theoperation of the system.

Furthermore, it should be appreciated that various links connectingelements can be wired or wireless links, or a combination thereof, orany known or later developed element(s) that is capable of supplyingand/or communicating data to and from the elements.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate exemplary, andseparately claimable, embodiment of the disclosure.

While exemplary aspects have been described in conjunction with a numberof embodiments, it is evident that many alternatives, modifications andvariations would be or are apparent to those of ordinary skill in theapplicable arts. Accordingly, this disclosure is intended to embrace allsuch alternatives, modifications, equivalents and variations that arewithin the spirit and scope of this disclosure.

1. A content analysis and malware prevention method comprising:receiving web content from one or more web servers; performing one ormore of analyzing and modifying of the web content; modifying, by aprocessor, any content identified as malware; and providing the webcontent to a web browser application for rendering and display.
 2. Themethod of claim 1, further comprising a receiving a request for webcontent from the web browser application.
 3. The method of claim 1,further comprising supplementing the web content with indicatorsregarding a vulnerability of one or more links within the web content.4. The method of claim 1, wherein the analysis of the web contentincludes include one or more of URL (Uniform Resource Locator) analysis,IP (Internet Protocol) analysis, image analysis, and script/HTMLanalysis.
 5. The method of claim 1, further comprising determiningwhether a request for the web content from the web browser applicationis a first request.
 6. The method of claim 1, further comprisingperforming one or more of pre-process data decryption, de-chinking anddecompressing.
 7. The method of claim 1, wherein the analysis is aprotocol-level analysis.
 8. The method of claim 1, further comprisingassembling a modified version of the web content and providing themodified version of the web content to the web browser application. 9.The method of claim 1, further comprising performing cloud verificationof the web content.
 10. The method of claim 1, further comprisingallocating memory for caching of the web content.
 11. A content analysisand malware prevention system comprising: a protection agent andprocessor that: receive web content from one or more web servers;perform one or more of analysis and modification of the web content;modify any content identified as malware; and provide the web content toa web browser application for rendering and display.
 12. The system ofclaim 11, wherein a request for web content is received from the webbrowser application.
 13. The system of claim 11, wherein the protectionagent further supplements the web content with indicators regarding avulnerability of one or more links within the web content.
 14. Thesystem of claim 11, wherein the analysis of the web content includesinclude one or more of URL (Uniform Resource Locator) analysis, IP(Internet Protocol) analysis, image analysis, and script/HTML analysis.15. The system of claim 11, wherein the protection agent furtherdetermines whether a request for the web content from the web browserapplication is a first request.
 16. The system of claim 11, wherein theprotection agent further performs one or more of pre-process datadecryption, de-chinking and decompressing.
 17. The system of claim 11,wherein the analysis is a protocol-level analysis.
 18. The system ofclaim 11, further comprising a browser engine that receives a modifiedversion of the web content and provides the modified version of the webcontent to the web browser application.
 19. The system of claim 11,further comprising a security center that performs cloud verification ofthe web content.
 20. The system of claim 11, wherein memory for cachingof the web content is allocated by the protection agent.